Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: modify Fluent Editor to TinyEditor #212

Merged
merged 2 commits into from
Jan 17, 2025

Conversation

kagol
Copy link
Member

@kagol kagol commented Jan 17, 2025

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Rebranding

    • Renamed project from "Fluent Editor" to "TinyEditor" across documentation, configuration files, and demo components
    • Updated package references, installation instructions, and project descriptions
    • Modified copyright notice to reflect new project name
  • Documentation Updates

    • Refreshed README files, contribution guidelines, and API documentation
    • Updated installation commands and code examples
    • Maintained existing functionality while changing project branding

@kagol kagol added the documentation Improvements or additions to documentation label Jan 17, 2025
Copy link

coderabbitai bot commented Jan 17, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request involves a comprehensive rebranding effort, changing the project name from "Fluent Editor" to "TinyEditor" across multiple documentation files, configuration files, and demo components. The changes are primarily cosmetic, updating project names, titles, descriptions, and text references while maintaining the underlying functionality and code structure.

Changes

File Path Change Summary
.github/ISSUE_TEMPLATE/bug-report.yml Updated project name in bug report template description
CONTRIBUTING.md, CONTRIBUTING.zh-CN.md Replaced all "Fluent Editor" references with "TinyEditor"
LICENSE Updated copyright notice to reference TinyEditor Authors
README.md, README.zh-CN.md Renamed project references, installation commands, and code snippets
packages/docs/fluent-editor/ Updated documentation, demos, and configuration files to use TinyEditor name

Suggested reviewers

  • kagol

Poem

🐰 A Rabbit's Renaming Rhyme 🖋️
From Fluent to Tiny, a name so bright,
Editors dancing with editorial might,
Words flow free, no longer confined,
A new identity, carefully designed!
Hop along, little editor dear! 🚀


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 97cfcee and 016971c.

📒 Files selected for processing (26)
  • .github/ISSUE_TEMPLATE/bug-report.yml (1 hunks)
  • CONTRIBUTING.md (6 hunks)
  • CONTRIBUTING.zh-CN.md (6 hunks)
  • LICENSE (1 hunks)
  • README.md (4 hunks)
  • README.zh-CN.md (3 hunks)
  • packages/docs/fluent-editor/.vitepress/components/TranslateComponent.vue (3 hunks)
  • packages/docs/fluent-editor/.vitepress/config.ts (2 hunks)
  • packages/docs/fluent-editor/.vitepress/sidebar.ts (1 hunks)
  • packages/docs/fluent-editor/.vitepress/theme/index.ts (1 hunks)
  • packages/docs/fluent-editor/.vitepress/theme/style.css (1 hunks)
  • packages/docs/fluent-editor/demos/add-toolbar-item.vue (1 hunks)
  • packages/docs/fluent-editor/demos/basic-usage.spec.ts (1 hunks)
  • packages/docs/fluent-editor/demos/basic-usage.vue (1 hunks)
  • packages/docs/fluent-editor/demos/get-content-delta.vue (1 hunks)
  • packages/docs/fluent-editor/demos/get-content-html.vue (1 hunks)
  • packages/docs/fluent-editor/demos/readonly.vue (1 hunks)
  • packages/docs/fluent-editor/demos/set-content-delta.vue (1 hunks)
  • packages/docs/fluent-editor/demos/set-content-html.vue (1 hunks)
  • packages/docs/fluent-editor/docs/api/fluent-editor-class.md (1 hunks)
  • packages/docs/fluent-editor/docs/api/fluent-editor-instance.md (1 hunks)
  • packages/docs/fluent-editor/docs/api/options.md (2 hunks)
  • packages/docs/fluent-editor/docs/demo/markdown.md (1 hunks)
  • packages/docs/fluent-editor/docs/quick-start.md (6 hunks)
  • packages/docs/fluent-editor/docs/used-in-framework.md (3 hunks)
  • packages/docs/fluent-editor/index.md (1 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@kagol kagol merged commit b5847f6 into main Jan 17, 2025
1 of 2 checks passed
@kagol kagol deleted the kagol/modify-FluentEditor-to-TinyEditor branch January 17, 2025 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant